I have a Windows 7 PC. Let's call it ABC. It's a domain member. From other PCs, which are also members of the same domain, I tried the command net view \\abc\ipc$ but I always get error. From XP computer, I get System error 123 has occurred. The filename, directory name, or volume label syntax is incorrect. From Win7 computer, I get System error 53 has occurred. The network path was not found. I've checked everything that are related: "Server" service, NIC > .... > "File and printer sharing....", share.... I'm lost. Could somebody shed some light? Is there an exhaustive check-list?

To resolve this error, please verify the following points: - Check if you can ping from the you computer to another computer and from the other computer to your computer. Run ping test. - Check by disabling all the security software. - Check that you can ping with the CMD prompt the remote host (by its IP address), and that the host answers without significant packet loss. If the remote host does not answer, please check on the remote host the DNS properties. - Check on the local computer and on the remote host that there is no security hardware or software blocking or filtering the communication between the local and remote machines (firewall / antivirus / router ...). - Check also in the network center that the network discovery and file sharing is turned on. Ensure also that the remote registry service (execute services.msc) is enabled and started. - Make sure the remote host is visible from the Windows network neighborhood. If necessary, check the point above. - Ensure that File and Printer sharing for Microsoft networks is enabled on the remote host. - Please check also that the NetBIOS protocol is enabled in the network card properties of the remote host. - Ensure that you can access from your computer the administrative shares of the remote host, by entering for example in the Windows file explorer: \\ABC\ipc$ This posting is provided "AS IS" with no warranties or guarantees , and confers no rights.

Hi Horinius, I am writing as a courtesy to follow-up on this issue. Do you have any updates? If so, please let me know at your earliest convenience. I am standing by for your reply and am happy to be of further assistance. Thanks! J Regards, Linda TechNet Subscriber Support in forum If you have any feedback on our support, please contact tngfb@microsoft.com Please remember to click Mark as Answer on the post that helps you, and to click Unmark as Answer if a marked post does not actually answer your question. This can be beneficial to other community members reading the thread.

> Check if you can ping from the you computer to another computer and from the other computer to your computer. Run ping test. ping has replies from one PC to the other and vice versa > Check by disabling all the security software. I'm using newly installed XP and Win7 (in virtual machines). So I suppose the only "security software" is "Windows Firewall", which is stopped in both PC. > Check that you can ping with the CMD prompt the remote host (by its IP address), ..... I don't quite see the difference of this one from the first one. Anyway, ping is OK (no packet loss). > Check on the local computer and on the remote host that there is no security hardware or software blocking or filtering the communication... This is essentially the same thing as the second suggestion. No? > Check also in the network center that the network discovery and file sharing is turned on. Network discovery: ON File sharing: ON > Ensure also that the remote registry service (execute services.msc) is enabled and started. Started as well > Make sure the remote host is visible from the Windows network neighborhood. If necessary, check the point above. It is already Visible > Ensure that File and Printer sharing for Microsoft networks is enabled on the remote host. Already enabled as default > Please check also that the NetBIOS protocol is enabled in the network card properties of the remote host I've checked the "Enable NetBIOS over TCP/IP" option in both local and remote host. > Ensure that you can access from your computer the administrative shares of the remote host, by entering for example in the Windows file explorer: \\ABC\ipc$ That's the problem! This UNC leads to the error message: \\abc\ipc$ is not accessible. You might not have permissions to use this network resource........ A thing to note: if I use \\abc\, I can see all the normal shares. And of course, no problem when I type "net view \\abc\". It's only when I want to access IPC$ that I have the error.

Looks like I missed one detail. I verified the access to the ipc$ shared folder from my PC and I get the same error message. Try to access it locally (\\127.0.0.1\ipc$) and you will have the same problem. Sorry, but I don't think that there is a way to access this shared folder manually. The procedure I gave you previously can be used for normal shares and and the ipc$ share is not considered as a normal one. The IPC$ is a hidden share maintained by the Server service (Disabling the service will remove the share). The IPC$ share is used for Inter Proces Communication by using RPC (Remote Procedure Call), allowing the client to send different commands to the server: List all shares List all users List files within a share Stop/Start services ... Sorry but I don't think that there is a way to let this share accessible manually (\\abc\ipc$) because I did not found a way to change NTFS or share permissions. This posting is provided "AS IS" with no warranties or guarantees , and confers no rights.

I've just found where the problem is. It's my eyes :p In the check-list I was reading and following, I was asked to check net view \\abc and then further in the list, net use \\abc\ipc$ and I missed that little word which is "use" 8-) Sorry.